Design doc: add Declarative API section #32
Conversation
design-docs/Expiration.md
Outdated
|
|
||
| ### Schema directives | ||
|
|
||
| These directives will land in a `cache` v0.1 [Apollo Spec](https://specs.apollo.dev/). |
There was a problem hiding this comment.
How much could we reuse the server side@cacheControl?
https://www.apollographql.com/docs/apollo-server/performance/caching/
There was a problem hiding this comment.
Good callout! We could probably reuse it with a few remarks:
scopeis irrelevant on the client (can simply be ignored)- the meaning of applying the directive to a type is different to what I imagined here, but I think it may be equivalent
- this draft: value for the type's fields
- Apollo Server's version: value for all fields that are of the type
- trying to wrap my head around
inheritMaxAge- not sure why it's useful - we still need a "Field" version of the directive
There was a problem hiding this comment.
scopeis irrelevant on the client (can simply be ignored)
We could have cross-user cache. For an example, in Confetti, all the session data is PUBLIC, but the bookmarks are PRIVATE. We're not there yet but could be something?
Agree ignoring it for now is fine.
we still need a "Field" version of the directive
Yea, either @cacheControlField() or field definition extensions in the GraphQL 2.0 spec 🤓
Overall, agree that we could model things more precisely but the prospect of getting all of these for free from the backend is pretty enticing
No description provided.